Based on past job-hunting experiences, it usually takes at least around 20 interviews to find a suitable job, so there’s no need to rush—and no way to rush either.
There are generally two types of interviews. One is where they’ve already reviewed your resume and then schedule an interview, during which they don’t really “test” you but just have a conversation. The other is more like an assembly-line interview, where the interviewer looks at your resume for the first time during the interview and asks all sorts of specific questions. The first kind tends to be more promising, while the second usually doesn’t lead anywhere and is less reliable.
I don’t know what company it was. The interview lasted about ten minutes. They said I wasn’t a good fit for the position. Their project is about creating a new chain based on the Cosmos SDK, integrating EVM, and making some performance optimizations, since Evmos has performance bottlenecks. It sounds like they’re trying to compete with Evmos. They’re also exploring ZK Layer 2 directions. They said I lacked experience in this area, so I wasn’t a match.
They didn’t want to reveal which exchange they were from. The wallet product is similar to Binance’s built-in Web3 wallet—self-custodial, not a custodial wallet. They didn’t ask any in-depth technical questions, just some basic ones. Maybe wallet development usually only involves this kind of general knowledge.
A classic story: a traditional company trying to build a consortium blockchain and move toward Web3.
A pretty standard interview. The actual requirements were related to Web2 skills, focusing on Go language, database usage, and database migration.
They were hiring mainly to optimize RPC performance for Solana nodes, since current Solana RPC queries have about a 1-second delay. They’re looking to improve things on the code level and also handle node maintenance to ensure high availability.
Found out during the HR interview that the exchange is Coinstone. I felt I had a good chat with the interviewer. The HR said they’re still interviewing other candidates and need more time.
But honestly, I don’t think the interviewer was very technically competent. If someone like that were to be my superior, I don’t think I’d be very happy. So even if I get an offer, I might have to think twice. If I don’t get one, that’s fine too.
(Added on April 22, 2025) Just remembered and wanted to briefly add some of the conversation details from back then:
I said the principle behind mnemonic phrases is that there’s a predefined word list, and a few words are selected from this list as the mnemonic. The other person said that’s not how it works—a mnemonic is essentially a seed, and this seed can be expanded into a tree structure, with each node in the tree representing a public/private key pair.
I said the current standard for wallets is BIP-39. He said that’s incorrect—the standard for wallets is BIP-44.
He asked me: when the grep command on a server matches data, how many records does it display? Assuming there’s only one match. (This question led me to conclude that “the other person is not very technically competent.”)
I’m done searching…